Dedicated clouds configuration

After purchasing a dedicated cloud, you can add it to your account from the Cloud Management page.

note

To see this page, you must have the Dedicated Cloud features enabled, and have the appropriate permissions in your account.

Configuration

1. From the Integration page, click the Manage menu and select Cloud Management

   • Identify an available cloud from the list. (Based on your purchase details, these clouds are pre-provisioned for environment classification, disaster recovery (DR), and resource allocations).

2. Enter configuration details to customize your dedicated cloud

   • Cloud Name: Assign a name to identify your cloud.
   • CIDR Block (Optional): Define the CIDR block for your dedicated Cloud’s network. If not specified, the block will be 10.0.0.0/16. If your Dedicated Cloud has Disaster Recovery, you must also specify the CIDR block for that cloud, which must be different. Note that this value cannot be changed after cloud provisioning.
   • Web Server Ports: Choose which ports to enable on the web server. Port 443 is required, but you can enable or disable the following:
     • 80 used only for HTTP use cases
     • 443 used only for HTTPS use cases
     • 444 used only when leveraging the Boomi APIM gateway.
   • Custom DNS IP: IP address of the DNS server the cloud should use to resolve hostnames. If no custom DNS is provided, a public DNS will be used. Note that this value cannot be changed after cloud provisioning.
   
   
   note

   If an internal DNS Server is required, a VPN should be set up first so that the server is reachable for hostname resolution.

   
   

3. Finalize Configuration and start deployment process Boomi will automatically configure the cloud’s infrastructure environment, including pre-set parameters for cloud size, environment type, and disaster recovery (DR).

   • Review the configuration summary. Once confirmed, Boomi will begin deploying the Dedicated Cloud using the settings you’ve provided. This process takes about an hour.
   • Press the refresh button to update your cloud status.

4. Create a cloud attachment on your dedicated cloud

   • From the Runtime Management page or using the Runtime Management API.
   • Deploy processes on that attachment as you would with any other cloud.
   note

   You can reset your dedicated cloud after initial configuration. However, resetting a dedicated cloud deconstructs the cloud infrastructure and requires deleting all of the cloud attachments and execution history. While doing this lets you reconfigure certain aspects of the cloud, it does not let you change classification, region, DR, or Cloud option.

5. Optional - VPN configuration VPNs can be added to a Dedicated Cloud after it is deployed. You can add any number of VPN connections to a cloud. To set up a VPN connection, you must provide the following inputs:

   • VPN Name: Provide a unique name for the VPN connection.
   • Customer Peer IP: Specify the IP address of your network’s VPN endpoint. Peer IP must be different for each VPN on the network.
   • Local VPN CIDR Block: Define the CIDR block for your local network to facilitate routing. You must specify at least one CIDR block but can use more than one.
   • BGP ASN: Enter the Border Gateway Protocol Autonomous System Number (ASN) for your VPN connection. Be careful to use a unique ASN for any VPNs connecting to the same Customer Peer IP, even across multiple networks.
   • Select Update at the bottom of the page to finalize your changes. Any changes on the UI are temporary until the Update is submitted.
   • This process takes about an hour. Press the refresh button to update VPN status.

6. Create a cloud attachment in Runtime Management.

   • Select the dedicated cloud you just set up to create a cloud attachment.
   • Associate attachment to an environment.

7. SUCCESS! The Cloud is now configured and ready for use. With the Dedicated clouds installed and configured, you are now ready to execute integration processes.